Systems and methods for saving and presenting a state of a communication session

ABSTRACT

A system comprising a computer-readable storage medium storing at least one program, and a computer-implemented method for saving and presenting a state of a communication session are presented. The communication session may be established between a client device and an application server of a content publisher, and may include the presentation of content on the client device. In some embodiments, the method may include receiving user input to save a state of the communication session, and in response, temporarily storing session data representative of the state of the communication session for a predetermined duration of the communication session. The method may further include generating and presenting an interface that includes a visual representation of the session data, and allows a user to return to the saved state of the communication session.

TECHNICAL FIELD

This application relates to data processing. In particular, exampleembodiments may relate to systems and methods for saving a state of acommunication session.

BACKGROUND

Traditionally, users browsing online content may employ multiple screen,browser windows or tabs. For example, users may use multiple tabs in abrowser window to compare multiple similar products. Users who may wishto browse content online using a mobile device may be unable to employsuch a comparison strategy due to the limited screen space of mobiledevices.

Further, while browsing through content online, users may wish to returnto a previous state of their browsing experience (e.g., a previoussearch query). Current bookmarking technology provided by internetbrowsers allow users to “bookmark” (e.g., save) certain web pages.However, such bookmarking services are limited only to web pages and areoften unable to save the state of certain pages (e.g., checkout pages,filled out forms, etc.) with elements that may be time sensitive. Thus,in order to return to the desired previous state, users must recall andcompletely recreate the steps (e.g., keyword searches performed, itemsclicked, pages viewed or the like) that lead to the desired state.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a network diagram depicting a network system having aclient-server architecture configured for exchanging data over anetwork, according to an example embodiment.

FIG. 2 is a block diagram illustrating an example embodiment of multiplemodules forming a marketplace application, which is provided as part ofthe network system of FIG. 1.

FIG. 3 is a block diagram illustrating an example embodiment of multiplemodules forming a scratchpad application, which is provided as part ofthe network system of FIG. 1.

FIG. 4A is an interaction diagram depicting a communication sessionbetween a first client device, and an application server, consistentwith some embodiments.

FIG. 4B is an interaction diagram depicting a communication sessionbetween a second client device and an application server, consistentwith some embodiments.

FIG. 5A is an interface diagram depicting a communication session,consistent with some embodiments.

FIG. 5B is an interface diagram depicting a portion of a scratchpadinterface displaying session data, consistent with some embodiments.

FIG. 5C is an interface diagram depicting a scratchpad interfacedisplaying multiple sets of session data, consistent with someembodiments.

FIG. 5D is an interface diagram depicting restoring a state of acommunication session using session data, consistent with someembodiments.

FIG. 5E is an interface diagram depicting further exchanges of theexample communication session, consistent with some embodiments.

FIG. 5F is an interface diagram depicting a scratchpad interface inconjunction with search results returned in response to a search queryas a further exchange of the example communication session, consistentwith some embodiments.

FIG. 5G is an interface diagram depicting the scratchpad interface,consistent with alternative embodiments.

FIG. 5H is an interface diagram depicting a portion of the scratchpadinterface, consistent with additional alternative embodiments.

FIG. 6 is a flowchart illustrating an example method of storing andpresenting session data, consistent with some embodiments.

FIG. 7 is a flowchart illustrating an example method for storingadditional session data, consistent with some embodiments.

FIG. 8 is a flowchart illustrating an example method for deletingsession data, consistent with some embodiments.

FIG. 9 is a diagrammatic representation of a machine in the example formof a computer system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments forcarrying out the inventive subject matter. Examples of these specificembodiments are illustrated in the accompanying drawings. It will beunderstood that they are not intended to limit the scope of the claimsto the described embodiments. On the contrary, they are intended tocover alternatives, modifications, and equivalents as may be includedwithin the scope of the disclosure. In the following description,specific details are set forth in order to provide a thoroughunderstanding of the subject matter. Embodiments may be practicedwithout some or all of these specific details. In accordance with thepresent disclosure, components, process steps, and data structures maybe implemented using various types of operating systems, programminglanguages, computing platforms, computer programs, and/or generalpurpose machines.

Aspects of the present disclosure describe systems and methods forsaving and presenting a state of a communication session. Thecommunication session may be established between a client device and anapplication server of a content publisher, and may include thepresentation of content on the client device. For example, acommunication session may include searching, viewing, comparing, andpurchasing items offered for sale in an online marketplace. In someembodiments, the method may include receiving user input to save a stateof the communication session. The state of the communication session mayrepresent the entire context leading to and forming the condition of acommunication session at a particular time. The state of thecommunication session may include a series of actions performed by auser while being engaged in online activity (e.g., viewing a webpage,exchanging data with an application server, etc.). In response toreceiving the user input, session data representative of the state ofthe communication session may be stored for a predetermined duration,consistent with some embodiments. The method may further includegenerating an interface that includes a visual representation of thesession data, and allows a user to navigate back to the saved state ofthe communication session. In this manner, a user may be able to recalla state of the communication session without having to recreate the flow(e.g., the series of actions leading to the saved state) of thecommunication session. Further, the interface may allow a user toquickly compare multiple items in one interface. The method may furtherinclude providing instructions to the client device that cause theclient device to present the interface.

FIG. 1 is a network diagram depicting a network system 100, according toone embodiment, having a client-server architecture configured forexchanging data over a network. The network system 100 may include anetwork-based content publisher 102 in communication with client devices106 and 108, and third party server 114. For example, the network-basedcontent publisher 102 may be a network-based marketplace.

The network-based content publisher 102 may communicate and exchangedata within the network system 100 that may pertain to various functionsand aspects associated with the network system 100 and its users. Thenetwork-based content publisher 102 may provide server-sidefunctionality, via a network 104 (e.g., the Internet), to one or moreclient devices (e.g., client devices 106 and 108). The one or moreclient devices may be operated by users that use the network system 100to exchange data over a communication network 104. These transactionsmay include transmitting, receiving (communicating), and processing datato, from, and regarding content and users of the network system 100. Thedata may include, but are not limited to: images; video or audiocontent; user preferences; product and service feedback, advice, andreviews; product, service, manufacturer, and vendor recommendations andidentifiers; product and service listings associated with buyers andsellers; product and service advertisements; auction bids; andtransaction data, among other things.

In various embodiments, the data exchanged within the network system 100may be dependent upon user-selected functions available through one ormore client or user interfaces (UIs). The UIs may be associated with aclient device, such as a client device 106 using web client 110. The webclient 110 may be in communication with the network-based contentpublisher 102 via a web server 122. The UIs may also be associated witha client device 108 using scratchpad application 112, such as a clientapplication in communication with the network-based content publisher102, or a third party server 114 (e.g., one or more servers or clientdevices) hosting a third party application 116.

The client devices 106 and 108 may be any of a variety of types ofdevices. For example, the client devices 106 and 108 may a mobile devicesuch as a smartphone such as an iPhone® or other mobile device runningthe iOS® operating system, the Android® operating system, a BlackBerry®operating system, the Microsoft® Windows® Phone operating system,Symbian® OS, or webOS®. Consistent with some embodiments, the clientdevices 106 and 108 may alternatively be a tablet computer, such as aniPad® or other tablet computer running one of the aforementionedoperating systems. In some embodiments, the client device 106 and 108may also be a personal digital assistant (PDA), a personal navigationdevice (PND), a handheld computer, a desktop computer, a laptop ornetbook, a set-top box (STB) such as provided by cable or satellitecontent providers, a wearable computing device such as glasses or awristwatch, a multimedia device embedded in an automobile, a GlobalPositioning System (GPS) device, a data enabled book reader, or a videogame system console such as the Nintendo Wii®, the Microsoft Xbox 360®,or the Sony PlayStation 3®, or other video game system consoles.

The client devices 106 and 108 may interface via a connection 118 withthe communication network 104 (e.g., the Internet or Wide Area Network(WAN)). Depending on the form of the client device 106 and 108, any of avariety of types of connections 118 and communication networks 104 maybe used. For example, the connection 118 may be Code Division MultipleAccess (CDMA) connection, a Global System for Mobile communications(GSM) connection, or other type of cellular connection. Such aconnection 118 may implement any of a variety of types of data transfertechnology, such as Single Carrier Radio Transmission Technology(1xRTT), Evolution-Data Optimized (EVDO) technology, General PacketRadio Service (GPRS) technology, Enhanced Data rates for GSM Evolution(EDGE) technology, or other data transfer technology (e.g., fourthgeneration wireless, 4G networks). When such technology is employed, thecommunication network 104 may include a cellular network that has aplurality of cell sites of overlapping geographic coverage,interconnected by cellular telephone exchanges. These cellular telephoneexchanges may be coupled to a network backbone (e.g., the publicswitched telephone network (PSTN), a packet-switched data network, or toother types of networks).

In another example, the connection 118 may be Wireless Fidelity (Wi-Fi,IEEE 802.11x type) connection, a Worldwide Interoperability forMicrowave Access (WiMAX) connection, or another type of wireless dataconnection. In such an embodiment, the communication network 104 mayinclude one or more wireless access points coupled to a local areanetwork (LAN), a WAN, the Internet, or other packet-switched datanetwork. In yet another example, the connection 118 may be a wiredconnection, for example an Ethernet link, and the communication network104 may be a LAN, a WAN, the Internet, or other packet-switched datanetwork. Accordingly, a variety of different configurations areexpressly contemplated.

FIG. 1 also illustrates a third party application 116 executing on thethird party server 114 that may offer one or more services to users ofthe client devices 106 and 108. The third party application 116 may haveprogrammatic access to the network-based content publisher 102 via theprogrammatic interface provided by an application program interface(API) server 120. In some embodiments, the third party application 116may be associated with any organizations that may conduct transactionswith or provide services to the users of the client devices 106 and 108.

Turning specifically to the network-based content publisher 102, the APIserver 120 and a web server 122 are coupled to, and provide programmaticand web interfaces respectively to, one or more application servers 124.The application server 124 may, for example, host one or moremarketplace applications 126, which may provide a number of marketplacefunctions and services to users that access the network-based contentpublisher 102. The application server 124 may also host one or morescratchpad applications 128, which may be configured to store andgenerate scratchpad interfaces with session data representative of astate of a communication session. Such scratchpad interface may, forexample, be presented on one of the client devices 106 or 108.

The application server 124 may be coupled via the API server 120 and theweb server 122 to the communication network 104, for example, via wiredor wireless interfaces. The application server 124 is, in turn, shown tobe coupled to one or more database servers 130 that facilitate access toa database 132. In some examples, the application server 124 can accessthe database 132 directly without the need for a database server 130. Insome embodiments, the database 132 may include multiple databases thatmay be both internal and external to the network-based content publisher102.

While the marketplace application 126 and the scratchpad application 128are shown in FIG. 1 to both form part of the network-based contentpublisher 102, it will be appreciated that, in alternative embodiments,the scratchpad application 128 may form part of a service that isseparate and distinct from the network-based content publisher 102.Further, while the system 100 shown in FIG. 1 employs client-serverarchitecture, the present inventive subject matter is, of course, notlimited to such an architecture, and could equally well find applicationin an event-driven, distributed, or peer-to-peer architecture system,for example. The various modules of the application server 124 may alsobe implemented as standalone systems or software programs, which do notnecessarily have networking capabilities.

FIG. 2 is a block diagram illustrating an example embodiment of multiplemodules forming a marketplace application 126, which is provided as partof the network system of FIG. 1. The modules of the marketplaceapplication 126 may be hosted on dedicated or shared server machinesthat are communicatively coupled to enable communications between servermachines. Each of the modules 200-214 are communicatively coupled (e.g.,via appropriate interfaces) to each other and to various data sources,so as to allow information to be passed between the modules 200-214 ofthe marketplace application 126 or so as to allow the modules 200-214 toshare and access common data. The various modules of the marketplaceapplication 126 may furthermore access one or more databases 132 via thedatabase server 130 (FIG. 1).

The marketplace application 126 may provide a number of publishing,listing, and price-setting mechanisms whereby a seller may list (orpublish information concerning) goods or services for sale, a buyer canexpress interest in or indicate a desire to purchase such goods orservices, and a price can be set for a transaction pertaining to thegoods or services. To this end, the marketplace application 126 is shownto include at least one publication module 200 and at least one auctionmodule 202, which support auction-format listing and price settingmechanisms (e.g., English, Dutch, Vickrey, Chinese, Double, Reverseauctions etc.). The auction module 202 may also provide a number offeatures in support of such auction-format listings, such as a reserveprice feature whereby a seller may specify a reserve price in connectionwith a listing, and a proxy-bidding feature whereby a bidder may invokeautomated proxy bidding.

A number of fixed-price modules 204 support fixed-price listing formats(e.g., the traditional classified advertisement-type listing or acatalogue listing) and buyout-type listings. Specifically, buyout-typelistings (e.g., including the Buy-It-Now (BIN) technology developed byeBay Inc., of San Jose, Calif.) may be offered in conjunction withauction-format listings, and allow a buyer to purchase goods orservices, which are also being offered for sale via an auction, for afixed-price that is typically higher than the starting price of theauction.

A store module 206 may allow sellers to group their product listings(e.g., goods and/or services) within a “virtual” store, which may bebranded and otherwise personalized by and for the sellers. Such avirtual store may also offer promotions, incentives, and features thatare specific and personalized to a relevant seller. In one embodiment,the listings and/or transactions associated with the virtual store andits features may be provided to one or more users.

Navigation of the network-based content publisher 102 may be facilitatedby one or more navigation modules 208. For example, a search module may,inter alia, enable key word searches of listings published via thenetwork-based content publisher 102. A browser module may allow usersvia an associated UI to browse various category, catalogue, inventory,social network, and review data structures within the network-basedcontent publisher 102. Various other navigation modules 208 (e.g., anexternal search engine) may be provided to supplement the search andbrowsing modules. Consistent with some embodiments, the results for keyword searches of listings published via the network-based contentpublisher 102 may be filtered to include only listings corresponding tosocial network connections of the user (e.g., indicated friends andfamily).

In one embodiment, an electronic shopping cart module 210 is used tocreate an electronic shopping cart used by users of the network-basedcontent publisher 102 to add and store products (e.g., goods andservices) listed by the store module 206. The electronic shopping cartmodule 210 may also be used to “check out,” meaning a user may purchaseproducts in the electronic shopping cart. The electronic shopping cartmodule 210 may facilitate the transactions by automatically finding theproducts in the electronic shopping cart across at least one or all of apredefined set of vendors, a comparison shopping site, an auction site,etc. In various embodiments, the selection criteria for which vendor orvendors to purchase from may include, but are not limited to, criteriasuch as lowest cost, fastest shipping time, preferred or highest ratedvendors or sellers, or any combination thereof.

As illustrated in FIG. 2, the marketplace application 126 may include atleast one payment module 212 that may provide a number of paymentservices and functions to users. The payment module 212 may allow usersto accumulate value (e.g., in a commercial currency, such as the U.S.dollar, or a proprietary currency, such as “points”) in accounts, andthen later to redeem the accumulated value for products (e.g., goods orservices) that are made available via the payment module 212. For someexample embodiments, the payment module 212 generally enable transfer ofvalues (e.g., funds, reward points, etc.) from an account associatedwith one party (e.g., a sender) to another account associated withanother party (e.g., a receiver).

As illustrated in FIG. 2, the marketplace application 126 may include atleast one recommendation module 214, which may provide recommendationservices and functions to users. In some embodiments, the recommendationmodule 214 may receive requests for recommendations, and, in turn,provide a recommendation to the user based on information contained inthe user's corresponding user profile. In some embodiments, therecommendation module 214 may automatically generate and provide arecommendation based on the activity of the user. The recommendationsprovided by the recommendation module 214 may contain one or more items(e.g., products offered for sale, articles, blogs, movies, socialnetwork connections, etc.) that may potentially interest a user. Therecommendations may, for example, be based on previous productspurchased by the user or a social network connection of the user, a webpage viewed by the user, or an item given favorable feedback by the useror a social connection of the user.

FIG. 3 is a block diagram illustrating an example embodiment of multiplemodules forming scratchpad applications 112 and 128, which are providedas part of the network-based content publisher 102. The scratchpadapplications 112 and 128 are shown as including at least one user inputmodule 300, state module 302, and user interface module 304, allconfigured to communicate with each other (e.g., via a bus, sharedmemory, a switch, or application programming interfaces (APIs)). Thevarious modules of the scratchpad applications 112 and 128 may accessone or more databases 132 via the database server 130, and each of thevarious modules of the scratchpad applications 112 and 128 may each bein communication with one or more third party applications 116. Further,the various modules of the scratchpad applications 112 and 128 mayaccess a machine-readable memory of the client devices 106 and 108.

Consistent with some embodiments, the user input module 300 may beconfigured to receive user input generated by one or more input/output(I/O) devices that may be included with or communicatively coupled toone of the client devices 106 or 108. Depending on the form of theclient devices, the I/O devices may, for example, be a mouse, a trackpad, a keypad, a keyboard, a multi-touch sensing surface (e.g., atouchscreen or trackpad), a microphone, a speaker, a camera, and thelike. The user input may be received by one of the aforementioned I/Odevices and in some embodiments, transmitted to the application server124 for receipt by the user input module 300.

The state module 302 may be configured to capture and store session datathat is representative of a state of a communication session and may beused to recall the state of the communication session. Session datarefers to a series of steps, events or actions performed by a user whenvisiting a web site or performing another activity while using anapplication executing on a client device. Example session data includesevents that describe the actions performed by a user when conducting anonline transaction, completing an online form, taking an online survey,and participating in other online activities that involve two or moresteps performed by the user. The session data may include informationprovided by a user, buttons (or other visual indicators) activated bythe user, an identification of steps completed by the user, keystrokes,and cursor and pointer movements, actions canceled by the user, and soforth.

Consistent with some embodiments, the session data may includeclickstream data. Accordingly, the state module 302 may be configured tomonitor, track, and record the activities and interactions of a user,using one or more devices (e.g., client device 106), with the variousmodule of the network system 100. The session data may be captured bythe state module 302 and stored in response to the receipt of user input(e.g., received by the user input module 300) to signal the saving ofthe state of the communication session. The session data may be storedby the state module 302 as an XML-based text document, consistent withsome embodiments. In some embodiments, the session data may be stored bythe state module 302 in the database 132. In some embodiments, thesession data may be stored by the state module 302 in a machine-readablemedium of a client device of the user (e.g., client device 106 or 108).

The session data may further include interactions of a client devicewith the application server 124. Accordingly, the session data mayinclude requests made by a user and transmitted by the user's clientdevice to the application server 124. Consistent with some embodiments,the requests may, for example, include keyword search queries performed,requests for recommendations, web page view requests, requests to add aproduct to a user wish list, watch list or electronic shopping cart, orthe like. In some embodiments, the session data may also includeresponses to the user requests received from the application server 124.The responses may, for example, include keyword search results,recommendations, web pages, interfaces for a wish list, watch list orelectronic shopping cart, or the like. It will be appreciated that insome embodiments, the keyword searches, recommendations and web pagesmay correspond to one or more listings created and maintained by themarketplace application 126. The session data may further includecontextual information provided by an application executing on a clientdevice as part of the communication session.

The user interface module 304 may be configured to generate scratchpadinterfaces to be presented on a client device of a user. Upon generatingthe one or more scratchpad interfaces, the user interface module 304 maytransmit instructions to the client device that cause the client deviceto display the user interfaces. Consistent with some embodiments, theuser interface module 304 may generate a scratchpad interface to allow auser to quickly save, access, and compare items of interest to the user.The scratchpad interface may be displayed by a client device of the userin conjunction with one or more other scratchpad interfaces involved ina given communication session with the client device. The scratchpadinterface may include a display of the session data captured by thestate module 302 that is representative of the state of a communicationsession. A scratchpad interface may include multiple sets of sessiondata. Depending on the user's activity during a given data session, themultiple sets of session data may include both homogeneous andheterogeneous groups. For example, a homogeneous group of session datasets may include data related to a particular category of products(e.g., “digital cameras”), while a heterogeneous group of session datamay include data related to products from various categories of products(e.g., a digital camera, a holiday sweater, and a toaster).

In some embodiments, the scratchpad interface may include functionalityto allow a user to compare multiple items included in multiple sets ofsession data. In some embodiments, this functionality may be provided tousers upon receiving user input (e.g., received by the user input module300) requesting a comparison of a homogeneous group of session datasets. The comparison may include a comparison of various attributes ofitems included in session data. For example, the scratchpad interfacemay contain a homogeneous group of three sets of session data. The firstset of session data may relate to a first digital camera, the second setof session data may relate to a second digital camera, and the third setof session data may relate to a third digital camera. Following thisexample, the state module 302 may, upon receiving appropriate userinput, generate a display of the three sets of session data in a mannerfor convenient comparison of the three digital cameras including acomparison of a select set of attributes of each.

FIG. 4A is an interaction diagram depicting a communication sessionbetween a first client device and an application server, consistent withsome embodiments. The first client device illustrated in FIG. 4A is thefirst client device of at least two client devices belonging to a userand may, for example, correspond to the client device 106 or 108. Theapplication server may, for example, correspond to the applicationserver 124.

As shown, a communication session may be established between the firstclient device and the application server. In some embodiments, the usermay be instructed to log in or otherwise authenticate his identity aspart of establishing the communication session. The communicationsession may comprise multiple data exchanges over a network (e.g.,communication network 104) including the transmission of a plurality ofrequests by the first client device received by the application server.The application server may, in turn, transmit a plurality of responsesto the first client device in response to the aforementioned pluralityof requests. During the course of the communication session with thefirst client device, the user may identify an item of interest that theuser would like to revisit at a later time. Accordingly, the user,utilizing one of several possible I/O devices of the first clientdevice, may signal the application server, through appropriate userinput, to save the state of the communication session.

In response to receiving the user input, the application server maystore session data representative of the state of the data session in asession data repository (e.g., database 132). Further, the applicationserver may generate a scratchpad interface that includes a visualrepresentation of the session data. The application server may thentransmit instructions to the first client device that causes the clientdevice to display the scratchpad interface.

The first client device may present the scratchpad interface inconjunction with other content involved in the continued execution ofthe communication session. In addition to providing a visualrepresentation of the session data, the scratchpad interface presentedon the first client device may allow the user to return to a particularstate of the communication session through selection of the visualrepresentation of the session data. As shown, the application server mayreceive the user selection of the session data.

In response to receiving the user selection, the application server mayretrieve the session data from the session data repository. Theapplication server may then provide instructions to the first clientdevice that cause the first client device to recall and return to thestate of the communication session previously captured in response tothe user input. In this manner, the user may revisit the state of thecommunication session during which the user identified the item ofinterest.

As illustrated in FIG. 4A, the communication session between the firstclient device and the application server may subsequently be terminated.Consistent with some embodiments, in response to terminating thecommunication session, the application server may remove or delete thesession data stored in the data session repository, at which point thesession data may no longer be available for display in the scratchpadinterface during subsequent communication sessions.

FIG. 4B is an interaction diagram depicting a communication sessionbetween a second client device and an application server, consistentwith some embodiments. In particular, the second client device is thesecond of at least two client devices belonging to the user discussed inFIG. 4A, and may, for example, correspond to client device 106 or 108.Further, the various interactions between the second client device andthe application server illustrated in FIG. 4B may be performedsubsequent to the storing of session data discussed in FIG. 4A.

As shown in FIG. 4B, a communication session is established between thesecond client device and the application server. In some embodiments,the user may be instructed to log in or otherwise authenticate hisidentity as part of establishing the communication session. Thisauthentication may provide the application server with a linking betweenthe first client device and second client device and may provide theuser with access to the session data on the second client device, whichwas saved during the communication session with the first client device.Further, as part of establishing the communication session, theapplication server may provide the second client device withinstructions to present the scratchpad interface discussed in FIG. 4A.Utilizing an I/O device of the second client device, the user may selectthe visual representation of the session data (discussed in FIG. 4A)displayed in the scratchpad interface. The user selection is thentransmitted by the second client device and received by the applicationserver. In response to receiving the user selection, the applicationserver may retrieve the session data from the session data repository(e.g., databases 132) and transmit instructions the second client devicewhich cause the second client device to present the state of thecommunication session (e.g., originating on the first client device)represented by the session data.

FIG. 5A is an interface diagram depicting an example communicationsession, consistent with some embodiments. Consistent with someembodiments, the example communication session may take place betweenthe application server 124 and the client device 108 over communicationnetwork 104. As illustrated in FIG. 5A, the example communicationsession includes a search query 500 input by a user on an interfacedisplayed on the client device 108 (e.g., on a touchscreen of the clientdevice 108), which may be transmitted as a request to the applicationserver 124.

FIG. 5B is an interface diagram depicting further data exchanges of thecommunication session, consistent with some embodiments. As illustratedin FIG. 5B, search results 502 may be returned by the application server124 to the client device 108 in response to receiving the search query500. In particular, the search results 502 may include items 504-512. Asshown, each of the items 504-512 may correspond to a listing for aproduct offered for sale (e.g., published using the marketplaceapplication 126). Consistent with some embodiments, the user of theclient device 108 may, through appropriate touch gesture (e.g., doubletap), cause the scratchpad application 128 to capture and store a stateof the example communication session.

FIG. 5C is an interface diagram depicting a scratchpad interface 514displaying visual representations of session data, consistent with someembodiments. As illustrated, the scratchpad interface 514 may include anelement 516 comprising a hyperlink, which when activated throughappropriate user input (e.g., a tap), may cause the client device 108 toreturn to the display of search results 502 as illustrated in FIG. 5B.The scratchpad interface 514 may also include elements 518 and 520 thateach include a hyperlink corresponding to a product listings for items510 and 508, respectively, viewed during the communication session. Asshown, each of the elements 518 and 520 also include additionalinformation (e.g., a description) or content (e.g., a correspondingimage) associated with the items 510 and 508. The elements 516-520 arevisual representations of session data that has been saved by thescratchpad application 128 in response to receiving applicable userinput (e.g., a double tap). In particular, the session datacorresponding to element 516 may be saved by the scratchpad application128 in response to receiving appropriate user input while viewing thesearch results 502 as illustrated in FIG. 5B. Similarly, the sessiondata corresponding elements 518 and 520 may be saved by the scratchpadapplication 128 in response to receiving appropriate user input whileviewing the listing pages corresponding to items 510 and 508,respectively.

The scratchpad interface 514 may further include tab 518, which may beused to hide or expand the scratchpad interface 514. In someembodiments, the scratchpad interface 514 may be hidden or expanded viaa touch gesture swipe to the left or right of the display of the clientdevice 108. The tab 518 may also be used to move the location of thescratchpad interface to the top, bottom or left of the display. Thescratchpad interface may also include button 522, which may be used tovisually compare items displayed on the scratchpad interface 514.

FIG. 5D is an interface diagram depicting a visual comparison of itemsdisplayed on the scratchpad interface 514, consistent with someembodiments. Upon selection of the button 522, the scratchpadapplication 128 may cause the set of attributes 524 and 526 to bedisplayed on the scratchpad interface 514 presented on the client device108. While FIG. 5D illustrates the attributes 524 and 526 as includingthree attributes, it shall be appreciated that in other embodiments, thenumber of attributes maybe more or fewer. Further, in other embodiments,items other than products offered for sale may be compared, and thedisplayed attributes may vary according to the item type.

FIG. 5E is an interface diagram depicting further exchanges of theexample communication session, consistent with some embodiments. Asillustrated in FIG. 5E, the example exchange session may include afurther search query 550 performed subsequent to the search query 500.The search results 552 may be returned by the application server 124 tothe client device 108 in response to receiving the search query 550. Asshown, the majority of scratchpad interface 514 may be hidden whileviewing the search results 552. A small portion of the scratchpadinterface 514 (e.g., a tab) may, however, continue to be displayed whileviewing the search results 552.

FIG. 5F is an interface diagram depicting the scratchpad interface 514in conjunction with the search results 552 returned in response to thesearch query 550 as a further exchange of the example communicationsession, consistent with some embodiments. As shown, the scratchpadinterface 514 may be displayed in conjunction with the search results552 in response to the user dragging (e.g., by touch gesture) theportion of the scratchpad interface 514 across the display of the clientdevice 108. Although the user of the client device 108 may continue tosearch for other items during the example communication session, thescratchpad interface 514 may continue to include the elements discussedin reference to FIGS. 5C and 5D.

FIG. 5G is an interface diagram depicting the scratchpad interface 514,consistent with some alternative embodiments. As shown, the scratchpadinterface 514 may be displayed as a banner overlaid on an unobtrusiveportion of the user interface. According to this alternative embodiment,the scratchpad interface 514 may include the elements 516 g-520 g whichare visual representations (e.g., icons) of session data that has beensaved by the scratchpad application 128 in response to receivingapplicable user input (e.g., a double tap). Selection of one of theelements 516 g-520 g may cause the recall of the corresponding savedstate of the communication session.

FIG. 5H is an interface diagram depicting the visual representations ofsaved session data, consistent with additional alternative embodiments.In particular, FIG. 5H illustrates elements 516 h, 518 h, and 520 h,which are visual representations of session data representative of thestate of the communication session saved by the scratchpad application128, consistent with alternative embodiments. As shown, the elements 516h, 518 h, and 520 h may be displayed independently of the scratchpadinterface 514. Further, each of the elements 516 h, 518 h, and 520 h maybe moved to any portion of the user interface through user manipulation.Selection of one of the elements 516 h-520 h may cause the recall of thecorresponding saved state of the communication session.

FIG. 6 is a flowchart illustrating an example method 600 of storing andpresenting session data, consistent with some embodiments. The method600 may be embodied in computer-readable instructions for execution byone or more processors such that the steps of the method 600 may beperformed in part or in whole by the application server 124 or theclient devices 106 and 108 and, in particular, the modules 300-304comprising the scratchpad applications 112 and 128.

At operation 605, a communication session may be established between theclient device 106 or 108 and the application server 124. Thecommunication session may include multiple data exchanges including aplurality of requests received from the client device 106 or 108 and aplurality of responses transmitted by the application server 124 inresponse to the requests. For example, a user of the client device 108may transmit a keyword search request for products listed for sale usingthe marketplace application 126. In turn, the application server 124 mayrespond with a number of search results for products matching the user'skeyword search request. At operation 610, the user input module 300 mayreceive user input from the client device 106 or 108 requesting that aparticular state of the communication session be saved for later access.In some embodiments, the user input may be a touch gesture received on amulti-touch sensing surface of the client device 106 or 108. The touchgesture may, for example, be a tap, a double tap, a long press, a pan, aflick, a two finger tap, a pinch open, or the like.

At operation 615, the state module 302 may, in response to the receivingof the user input, cause session data representative of the state of thecommunication session to be temporarily stored for a predeterminedamount of time. The session data may be stored in the database 132, orin some embodiments, in a machine-readable medium of the client device106 or 108 until an expiration time period has passed. Following theexample from above, upon receiving the search results for productsmatching the user's keyword search request, the user may, for example,double tap the search results displayed on a touchscreen of the clientdevice 108. This user input may then be provided to the user inputmodule 300, and in response the state module 302 may capture andtemporarily store the search results as session data in the database132.

At operation 620, the user interface module 304 may generate ascratchpad interface including a visual representation of the sessiondata. The scratchpad interface may present the session data such thatthe user may select a particular set of session data, and in turn, thestate of the communication session represented by the session data maybe restored. The scratchpad interface may further allow a user tocompare sets of session data and certain items contained therein.Following the example above, the user interface module 304 may generatea scratchpad interface that includes a textual detail of a selection ofthe search results. Moreover, because the keyword search query was forproducts and the search results were products, the scratchpad interfacemay allow a user to quickly compare the products contained therein.

At operation 625, the user interface module 304 may provide instructionsto the client device 106 or 108, which cause the device to present thescratchpad interface. The scratchpad interface may be displayed inconjunction with other content related to the communication session,consistent with some embodiments. Consistent with some embodiments, thevisual representation of the session data may include a hyperlink thatwhen activated through user input causes the client device 106 or 108 toreturn to the state of the communication session represented by thesession data. As illustrated in FIG. 6, the method 600 may includeoptional operations 630 and 635. At operation 630, a selection ofsession data (e.g., a hyperlink) made by the user may be received by theuser input module 300. In response to the user selection (e.g.,activating the hyperlink), the state of the communication sessionrepresented by the session data may be restored at operation 635.Following the example from above, the scratchpad presented on the clientdevice 108 may include a hyperlink, which when selected by the user,causes the client device 108 to return to the original search queryresults page.

FIG. 7 is a flowchart illustrating an example method for storingadditional session data, consistent with some embodiments. The method700 may be embodied in computer-readable instructions for execution byone or more processors such that the steps of the method 700 may beperformed in part or in whole by the application server 124 or theclient devices 106 and 108 and, in particular, the modules 300-304comprising the scratchpad applications 112 and 128. Further, the method700 may commence subsequent to the completion of method 600, consistentwith some embodiments.

At operation 705, the user input module 300 may receive an additionaluser input to save an additional state of the communication session thatis distinct from the session data stored at operation 615 of method 600.The user input may be received in accordance with the methodologiesdiscussed above in reference to method 600. In response to receipt ofthe user input, the state module 302 may cause additional session datarepresentative of the additional state of the communication session tobe temporarily stored at operation 710. The additional session data maybe temporarily stored in the database 132, or in some embodiments, in amachine-readable medium of the client device 106 or 108. The additionalsession data may be stored until an expiration time period has passed.At operation 715, the user interface module 304 may transmitinstructions to the client device 106 or 108 that cause the scratchpadinterface to be updated to include the additional session data.

Following the example presented in reference to FIG. 6, the user maycontinue the communication session on the client device 108 with theapplication server 124 and in doing so perform an additional keywordsearch for an another product. Upon receiving the search results at theclient device 108 from the application server 124, the user may save theadditional state of the communication session by again double tappingthe search results. In response to the user input, the state module 302may cause session data representative of the additional search resultsto be temporarily saved. Further, the scratchpad interface may byupdated by the user input module 300 to include the additional searchresults.

FIG. 8 is a flowchart illustrating an example method for deletingsession data, consistent with some embodiments. The method 800 may beembodied in computer-readable instructions for execution by one or moreprocessors such that the steps of the method 800 may be performed inpart or in whole by the application server 124 or the client devices 106and 108 and, in particular, the modules 300-304 comprising thescratchpad applications 112 and 128. Further, the method 800 maycommence subsequent to the completion of method 600 or 700, consistentwith some embodiments.

Consistent with some embodiments, the state module 302 may cause sessiondata to be temporarily stored in the database 132 until an expirationtime period has elapsed. At operation 805, the state module 302 maydetermine that the expiration time period has elapsed. Consistent withsome embodiments, the expiration time period may be the duration of thecommunication session, and in such embodiments, the operation 805comprises determining that the communication session has terminated. Insome embodiments, the expiration time period may be a default value or avalue set by a user.

At operation 810, the state module 302 may cause the stored session datato be deleted in response to determining that the expiration time periodhas elapsed. In some embodiments, if the client device 106 or 108 isstill engaged in a communication session, the user interface module 304may, at operation 815, transmit instructions to the client device 106 or108 that cause the device to refresh the scratchpad interface. Uponbeing refreshed, the scratchpad interface will no longer include visualrepresentations of the session data for which the expiration time periodhas elapsed, and in turn, the user may no longer return to the state ofthe communication session represented by the expired session data.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client, or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a FPGA or an ASIC) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses that connect the hardware modules). In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment, or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), with these operations being accessiblevia a network (e.g., the Internet) and via one or more appropriateinterfaces (e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,for example, a computer program tangibly embodied in an informationcarrier, for example, in a machine-readable medium for execution by, orto control the operation of, data processing apparatus, for example, aprogrammable processor, a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site, or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry(e.g., a FPGA or an ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that both hardware and software architectures meritconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 9 is a diagrammatic representation of a machine in the example formof a computer system 900 within which a set of instructions 924 forcausing the machine to perform any one or more of the methodologiesdiscussed herein may be executed. The computer system 900 may correspondto client device 106, third party server 114, or application server 124,consistent with some embodiments. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a personal computer(PC), a tablet PC, a set-top box (STB), a PDA, a cellular telephone, asmart phone (e.g., iPhone®), a tablet computer, a web appliance, anetwork router, switch or bridge, or any machine capable of executinginstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein.

The example computer system 900 includes a processor 902 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 904 and a static memory 906, which communicate witheach other via a bus 908. The computer system 900 may further include avideo display unit 910 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 900 also includes one ormore input/output (I/O) devices 912, a location component 914, a diskdrive unit 916, a signal generation device 918 (e.g., a speaker), and anetwork interface device 920. The I/O devices 912 may, for example,include a keyboard, a mouse, a keypad, a multi-touch surface (e.g., atouchscreen or track pad), a microphone, a camera, and the like.

The location component 914 may be used for determining a location of thecomputer system 900. In some embodiments, the location component 914 maycorrespond to a GPS transceiver that may make use of the networkinterface device 920 to communicate GPS signals with a GPS satellite.The location component 914 may also be configured to determine alocation of the computer system 900 by using an internet protocol (IP)address lookup or by triangulating a position based on nearby mobilecommunications towers. The location component 914 may be furtherconfigured to store a user-defined location in main memory 904 or staticmemory 906. In some embodiments, a mobile location enabled applicationmay work in conjunction with the location component 914 and the networkinterface device 920 to transmit the location of the computer system 900to an application server or third party server for the purpose ofidentifying the location of a user operating the computer system 900.

In some embodiments, the network interface device 920 may correspond toa transceiver and antenna. The transceiver may be configured to bothtransmit and receive cellular network signals, wireless data signals, orother types of signals via the antenna, depending on the nature of thecomputer system 900.

Machine-Readable Medium

The disk drive unit 916 includes a machine-readable medium 922 on whichis stored one or more sets of data structures and instructions 924(e.g., software) embodying or used by any one or more of themethodologies or functions described herein. The instructions 924 mayalso reside, completely or at least partially, within the main memory904, static memory 906, and/or within the processor 902 during executionthereof by the computer system 900, with the main memory 904 and theprocessor 902 also constituting machine-readable media.

Consistent with some embodiments, the instructions 924 may relate to theoperations of an operating system (OS). Further, the instructions 924may relate to operations performed by applications (commonly known as“apps”), consistent with some embodiments. One example of such anapplication is a mobile browser application that displays content, suchas a web page or a user interface using a browser.

While the machine-readable medium 922 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore data structures or instructions 924. The term “machine-readablemedium” shall also be taken to include any tangible medium that iscapable of storing, encoding, or carrying instructions (e.g.,instructions 924) for execution by the machine and that cause themachine to perform any one or more of the methodologies of the presentdisclosure, or that is capable of storing, encoding or carrying datastructures used by or associated with such instructions. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, solid-state memories, and optical and magnetic media.Specific examples of machine-readable media include non-volatile memory,including by way of example, semiconductor memory devices (e.g.,erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM)) and flash memory devices;magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks.

Furthermore, the tangible machine-readable medium is non-transitory inthat it does not embody a propagating signal. However, labeling thetangible machine-readable medium as “non-transitory” should not beconstrued to mean that the medium is incapable of movement—the mediumshould be considered as being transportable from one real-world locationto another. Additionally, since the machine-readable medium is tangible,the medium may be considered to be a machine-readable device.

Transmission Medium

The instructions 924 may further be transmitted or received over acommunications network 926 using a transmission medium. The instructions924 may be transmitted using the network interface device 920 and anyone of a number of well-known transfer protocols (e.g., HTTP). Examplesof communication networks include a LAN, a WAN, the Internet, mobiletelephone networks, POTS networks, and wireless data networks (e.g.,WiFi and WiMax networks). The term “transmission medium” shall be takento include any intangible medium that is capable of storing, encoding,or carrying instructions 924 for execution by the machine, and includesdigital or analog communications signals or other intangible media tofacilitate communication of such software.

Although the embodiments of the present invention have been describedwith reference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader scope of the inventive subjectmatter. Accordingly, the specification and drawings are to be regardedin an illustrative rather than a restrictive sense. The accompanyingdrawings that form a part hereof, show by way of illustration, and notof limitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be used and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. This DetailedDescription, therefore, is not to be taken in a limiting sense, and thescope of various embodiments is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

All publications, patents, and patent documents referred to in thisdocument are incorporated by reference herein in their entirety, asthough individually incorporated by reference. In the event ofinconsistent usages between this document and those documents soincorporated by reference, the usage in the incorporated referencesshould be considered supplementary to that of this document; forirreconcilable inconsistencies, the usage in this document controls.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended; that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim are still deemed to fall within thescope of that claim. Moreover, in the following claims, the terms“first,” “second,” and “third,” and so forth are used merely as labels,and are not intended to impose numerical requirements on their objects.

What is claimed:
 1. A system comprising: a processor of a machine; amachine-readable storage medium storing: a user input module configuredto receive a user input to save a state of a communication session, thecommunication session being established with a first client device of auser, the communication session including presentation of content on thefirst client device; a state module configured to temporarily storesession data representative of the state of the communication session,in response to receiving the user input, for a duration of thecommunication session; and a user interface module configured togenerate a scratchpad interface comprising a visual representation ofthe session data, the scratchpad interface allowing the user to returnto the saved state of the communication session through selection of thevisual representation of the session data, the user interface modulefurther configured to provide instructions to the first client devicethat cause the first client device to present at least a portion of thescratchpad interface in conjunction with the presentation of thecontent.
 2. The system of claim 1, wherein the user interface module isfurther configured to provide instructions to a second client devicethat cause the second client device to present the scratchpad interface,wherein a communication session is established with the second clientdevice.
 3. The system of claim 1, wherein the state module is furtherconfigured to delete the session data in response to the userterminating the communication session.
 4. The system of claim 3, whereinthe user input is a touch-based gesture received on a multi-touch inputsurface of the first client device.
 5. The system of claim 1, whereinthe session data includes clickstream data from the communicationsession.
 6. The system of claim 1, wherein the scratchpad interfaceincludes a link that when activated causes the first client device torestore the state of the communication session represented by thesession data.
 7. The system of claim 1, wherein the user input module isfurther configured to receive an additional user input to save anadditional state of the communication session; and wherein the statemodule is further configured to store additional session datarepresentative of the additional state of the communication session forthe duration of the communication session.
 8. The system of claim 7,wherein the scratchpad interface further includes a comparison of thesession data and the additional session data.
 9. A method comprising:establishing a communication session with a first client device of auser, the communication session including presenting content on thefirst client device; receiving user input to save a state of thecommunication session; in response to receiving the user input,temporarily storing session data representative of the state of thecommunication session for a duration of the communication session;generating a scratchpad interface including a visual representation ofthe session data, the scratchpad interface providing the ability torecall the saved state of the communication session through selection ofthe displayed session data; and providing instructions to the firstclient device that cause the first client device to present thescratchpad interface in conjunction with the presentation of thecontent.
 10. The method of claim 9, further comprising: establishing acommunication session with a second client device of the user, thecommunication session including presentation of content on the firstclient device of the user; and providing instructions to the secondclient device that cause the second client device to present thescratchpad interface on the second client device of the user inconjunction with the content.
 11. The method of claim 9, furthercomprising: determining an expiration time period has elapsed; and inresponse to determining the expiration time period has elapsed, deletingthe session data.
 12. The method of claim 9, wherein the user input is atouch-based gesture received on a multi-touch input surface of the firstclient device.
 13. The method of claim 9, wherein the session dataincludes a plurality of requests received from the first client device.14. The method of claim 13, wherein the plurality of requests includessearch queries performed by the user.
 15. The method of claim 14,further comprising: receiving a user selection of the visualrepresentation of the session data; and restoring the state of thecommunication session.
 16. The method of claim 9, further comprising:receiving an additional user input to save an additional state of thecommunication session; in response to receiving the additional userinput, temporarily storing additional session data representative of theadditional state of the communication session for the duration of thecommunication session; and providing instructions to the first clientdevice that cause the first client device to update the scratchpadinterface to include a visual representation of the session data. 17.The method of claim 16, wherein the user input is dragging a portion ofthe content displayed as part of the communication session into thescratchpad interface.
 18. The method of claim 16, further comprisingproviding instructions to the first client device that cause the firstclient device to present a comparison of the session data to theadditional session data.
 19. The method of claim 18, wherein the sessiondata and additional session data include an item offered for sale, eachof the items offered for sale having at least one item attribute; andwherein the presenting of the comparison of the session data with theadditional session data includes presenting the at least one itemattribute of each item offered for sale.
 20. A non-transitorymachine-readable storage medium embodying instructions that, whenexecuted by a machine, cause the machine to perform operationscomprising: establishing a communication session with a client device,the communication session including presenting content on the clientdevice; receiving user input to save a state of the communicationsession; in response to receiving the user input, temporarily storingsession data representative of the state of the communication sessionfor a duration of the communication session; generating a scratchpadinterface including a visual representation of the session data, thescratchpad interface providing the ability to recall the saved state ofthe communication session through selection of the visual representationof the session data; and providing instructions to the first clientdevice that cause the first client device to present the scratchpadinterface in conjunction with the presentation of the content.